Summary

Follow-up to the Renderer discovery caching PR. This pass eliminates four confirmed hot-path costs in HandlerService, RoutingService, and Router — all on the per-request critical path with no API surface changes.

Issue 1 — HandlerService: cache ImplicitViews setting (high impact)

onConfigurationLoad() already caches every framework setting into variables.* but was missing ImplicitViews. The getHandler() method was calling controller.getSetting("ImplicitViews") on every handler dispatch where the action does not exist in the handler CFC.

Fix: Add variables.implicitViews = variables.controller.getSetting("ImplicitViews") to onConfigurationLoad() and replace the per-request call in getHandler().

Issue 2 — HandlerService: eliminate redundant fileExists(expandPath()) in isViewDispatch() (high impact)

isViewDispatch() was calling fileExists(expandPath(targetView)) after locateView() / locateModuleView() had already verified file existence. Those methods encode existence in their return value: a path with a .cfm/.bxm extension means the file was found; a bare name without extension means not found.

Fix: Replace the filesystem call with an extension check — zero I/O:

if ( right( targetView, 4 ) == ".cfm" || right( targetView, 4 ) == ".bxm" ) {

This also fixes a latent bug where locateModuleView() appends .bxm for BoxLang views but the old code only checked for .cfm.

Issue 3 — RoutingService: use cached canDebug in findRoute() (medium impact)

findRoute() cached getLogger().canDebug() into a local canDebug variable at the top of the method, but two downstream branches re-called getLogger().canDebug() (and getLogger()) instead of using the already-cached value.

Fix: Replace both stray getLogger().canDebug() calls with canDebug.

Issue 4 — Router/RoutingService: pre-parse route response placeholders at registration (medium impact)

renderResponse() ran reMatchNoCase("{[^{]+?}", aRoute.response) and reReplaceNoCase(...) on every request for routes with a string response value. Route definitions are immutable after registration, so the placeholder list never changes.

Fix (two-part):

• Router.cfc addRoute() — pre-parse {token} placeholders into route.responsePlaceholders = [{token, key}, ...] at registration time.
• RoutingService.cfc renderResponse() — iterate the pre-parsed list; no regex at render time.

This also fixes a latent bug in the original loop where each iteration replaced in aRoute.response rather than the accumulated theResponse, so only the last placeholder's substitution survived when a response contained multiple tokens.

Test Coverage

• HandlerServiceTest.cfc — 3 new specs in a "Hot-path caching optimizations" describe block:
  • variables.implicitViews is a boolean cached after onConfigurationLoad()
  • isViewDispatch returns true for a view detected by extension
  • isViewDispatch returns false for a non-existent view
• RouterTest.cfc — 5 new specs in a "Response placeholder pre-parsing" describe block:
  • Single placeholder parsed correctly
  • Multiple placeholders all parsed
  • String response with no placeholders produces empty array
  • Closure response produces empty responsePlaceholders
  • Route with no response produces empty responsePlaceholders

Files Changed

Generated by Claude Code